NetApp
Cluster : Storage > Aggregates : Understanding aggregates : Requirements for performing a volume move

Requirements for performing a volume move
Before you move a volume nondisruptively, you must be aware of the types of volumes you can move and the operations that might conflict with the volume move. The volume move does not start if the volume has unsupported settings or if there are conflicting operations.
•
•
•
•
•
•
•
•
•
During a volume move, you must not initiate qtree SnapMirror or SnapVault relationships from the destination volume.
•
•
•
There is a small window of time when you can export the source volume over NFS or CIFS before the volume move enters the cutover phase. However, if you do so, the cutover phase might not be successfully completed. If the cutover phase is not completed, there is no disruption to iSCSI clients because the volume move rolls back to continue with the data copy phase.
•
The volume guarantee option must not be set to file.
•
If deduplication is active, the volume move is paused and the cutover phase is not initiated.
For more information about deduplication operations, see the Clustered Data ONTAP Logical Storage Management Guide.
•
•
•
•
•
Note: FlexClone volumes in the source volume are not moved along with the source volume. Fingerprint databases and change logs in the source volume are moved along with the source volume.


Was this topic helpful? Send comments to NetApp.